<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="zh" xml:lang="zh" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<head>
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Task Descriptor: Define Assessment and Traceability Needs</title>
<meta name="uma.type" content="TaskDescriptor">
<meta name="uma.name" content="define_assessment_and_traceability_needs">
<meta name="uma.presentationName" content="Define Assessment and Traceability Needs">
<meta name="uma.guid" content="_xhg2cEoiEdqrjq4i3fchvA">
<meta name="element_type" content="TaskDescriptor">
<meta name="filetype" content="description">
<meta name="role" content="">
<link rel="StyleSheet" href="./../../css/default.css" type="text/css">
<script src="./../../scripts/ContentPageResource.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ContentPageSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ContentPageSubSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ActivityTreeTable.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ProcessElementPage.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/ContentPageToolbar.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/contentPage.js" type="text/javascript" language="JavaScript"></script><script src="./../../scripts/processElementData.js" type="text/javascript" language="JavaScript"></script><script type="text/javascript" language="JavaScript">
					var defaultQueryStr = '?proc={35359DDF-6361-43E5-8B1B-18D204DA8CFF}&path={35359DDF-6361-43E5-8B1B-18D204DA8CFF},{CD77CBDA-CC13-4593-BB81-41AF3FF7A84C},_xhg2cEoiEdqrjq4i3fchvA';
					var backPath = './../../';
					var imgPath = './../../images/';
					var nodeInfo=null;
					contentPage.preload(imgPath, backPath, nodeInfo, defaultQueryStr, true, true, false);
				</script>
</head>
<body>
<div id="breadcrumbs"></div>
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr>
<td valign="top">
<div id="page-guid" value="_xhg2cEoiEdqrjq4i3fchvA"></div>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr>
<td class="pageTitle" nowrap="true">Task Descriptor: Define Assessment and Traceability Needs</td><td width="100%">
<div align="right" id="contentPageToolbar"></div>
</td><td width="100%" class="expandCollapseLink" align="right"><a name="mainIndex" href="./../../index.htm"></a><script language="JavaScript" type="text/javascript" src="./../../scripts/treebrowser.js"></script></td>
</tr>
</table>
<table width="100%" border="0" cellpadding="0" cellspacing="0">
<tr>
<td class="pageTitleSeparator"><img src="./../../images/shim.gif" alt="" title="" height="1"></td>
</tr>
</table>
<div class="overview">
<table width="97%" border="0" cellspacing="0" cellpadding="0">
<tr>
<td width="50"><img src="./../../images/taskdes_lg_dgm32.gif" alt="" title=""></td><td>
<table class="overviewTable" border="0" cellspacing="0" cellpadding="0">
<tr>
<td valign="top">This task describes how to define the requirements for assessment and traceability, and the overall strategy that will be followed.</td>
</tr>
<tr>
<td>Based on Method Task: <a href="./../../rup/tasks/define_assessment_and_traceability_needs_19C5C9FE.html" guid="{F6F9BB36-5A72-421E-B195-8937E0C46AF8}">Define Assessment and Traceability Needs</a></td>
</tr>
</table>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Relationships</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<th class="sectionTableHeading" scope="row">Roles</th><td class="sectionTableCell" width="30%"><span class="sectionTableCellHeading">Main:
								</span>
<ul>
<li>
<a href="./../../rup/capabilitypatterns/rup_test_analyst_14D45A1D.html" guid="_CUXhLRi2Edq_uI8xTPML6g">测试分析人员</a>
</li>
</ul>
</td><td class="sectionTableCell" width="30%"><span class="sectionTableCellHeading">Additional:
								</span></td><td class="sectionTableCell"><span class="sectionTableCellHeading">Assisting:
								</span></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row">Inputs</th><td class="sectionTableCell" width="30%"><span class="sectionTableCellHeading">Mandatory:
								</span>
<ul>
<li>
<a href="./../../rup/capabilitypatterns/rup_test_plan_504277FE.html" guid="_CUXhKRi2Edq_uI8xTPML6g">测试计划</a>
</li>
<li>
<a href="./../../rup/capabilitypatterns/rup_iteration_plan_36D6E33.html" guid="_CUXhLhi2Edq_uI8xTPML6g">迭代计划</a>
</li>
</ul>
</td><td class="sectionTableCell" width="30%"><span class="sectionTableCellHeading">Optional:
								</span>
<ul>
<li>
<a href="./../../rup/capabilitypatterns/rup_cm_plan_902E4CF9.html" guid="_xhzKUUoiEdqrjq4i3fchvA">配置管理计划</a>
</li>
<li>
<a href="./../../rup/capabilitypatterns/rup_project_plan_97493A67.html" guid="_s10jY0oiEdqrjq4i3fchvA">软件开发计划</a>
</li>
<li>
<a href="./../../rup/capabilitypatterns/rup_requirements_management_plan_85906CE9.html" guid="_xhzKUEoiEdqrjq4i3fchvA">需求管理计划</a>
</li>
</ul>
</td><td class="sectionTableCell"><span class="sectionTableCellHeading">External:
								</span>
<ul>
<li>None</li>
</ul>
</td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row">Outputs</th><td class="sectionTableCell" colspan="3">
<ul>
<li>
<a href="./../../rup/capabilitypatterns/rup_test_plan_504277FE.html" guid="_CUXhKRi2Edq_uI8xTPML6g">测试计划</a>
</li>
</ul>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Steps</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr>
<td class="sectionTableCell">
<div class="stepHeading"> Identify Assessment and Traceability Requirements </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="IdentifyAssessmentTraceRequirements" name="IdentifyAssessmentTraceRequirements"></a>
<div align="left">
    <table border="1" width="100%" cellspacing="0" cellpadding="4" style="border: 1px solid rgb(128,128,128)"     bordercolorlight="#808080" bordercolordark="#808080">
        <tr>
            <td width="5%">
                <b>Purpose:</b>&nbsp;
            </td>
            <td width="95%">
                To understand the deliverables for the software assessment process and elicit the associated
                requirements.&nbsp;
            </td>
        </tr>
    </table><br />
</div>
<p>
    Review the Iteration Plan and identify specific assessment needs for this forthcoming body of work. Ask stakeholders
    what they require from both assessment and traceability.
</p>
<p>
    Also, consider whether the test effort will be formally audited either during or at the conclusion of the testing
    effort. Formal audit requirements might necessitate the retention of additional documentation and records as proof that
    sufficient testing has been undertaken.
</p></td>
</tr>
</table>
</div>
<div class="stepHeading"> Consider Constraints </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="ConsiderConstraints" name="ConsiderConstraints"></a>
<div align="left">
    <table border="1" width="100%" cellspacing="0" cellpadding="4" style="border: 1px solid rgb(128,128,128)"     bordercolorlight="#808080" bordercolordark="#808080">
        <tr>
            <td width="5%">
                <b>Purpose:</b>&nbsp;
            </td>
            <td width="95%">
                To identify the constraints that will effect the ability (or the necessity) to implement the
                requirements.&nbsp;
            </td>
        </tr>
    </table><br />
</div>
<p>
    While there is typically a unending list of "wants" you might be tempted to consider as requirements for traceability
    and assessment strategies, it's important to focus on the most important "needs" that a) Provide essential information
    to the project team and b) Can actually be tracked and measured. It is unlikely that you will have enough resource
    available for your strategy to cater for more than what is essentially needed.
</p>
<p>
    <b>Sub-topics:</b>
</p>
<ul>
    <li>
        <a href="#ConsiderQualityLevel">Acceptable quality level</a>
    </li>
    <li>
        <a href="#ConsiderEnablers">Process and tool enablement</a>
    </li>
</ul>
<h4>
    <a id="ConsiderQualityLevel" name="ConsiderQualityLevel">Acceptable quality level</a> <a href="#ConsiderConstraints"><img src="./../../rup/resources/top.gif" alt="To top of page" border="0" width="26"     height="20" /></a>
</h4>
<p>
    It's important to identify what level of quality will be considered "good enough," and develop an appropriate
    assessment strategy. Note that often quality dimensions wax and wane in importance and quality levels rise and fall in
    the eyes of the stakeholders throughout the project lifecycle
</p>
<p>
    Review the QA Plan, review the Software Development Plan and interview the important stakeholders themselves directly
    to determine what they consider will be an acceptable quality level.
</p>
<h4>
    <a id="ConsiderEnablers" name="ConsiderEnablers">Process and tool enablement</a> <a href="#ConsiderConstraints"><img     src="./../../rup/resources/top.gif" alt="To top of page" border="0" width="26" height="20" /></a>
</h4>
<p>
    While you can probably imagine a world of effortless traceability and assessment at a low-level of granularity, the
    reality is that it's difficult and usually uneconomic to implement such approaches. With sophisticated tool support, it
    can still be difficult and time-consuming to manage low-level approaches to traceability; without supporting tools,
    almost impossible. The software engineering process itself might place constraints on traceability: for example, if
    traceability from tests to motivating requirements is desired, but the requirements themselves are not being carefully
    managed, it might be impossible to implement this traceability.
</p>
<p>
    Consider the constraints and limitations of both your software engineering process and tools, and choose an
    appropriate, workable traceability and assessment approach accordingly.
</p></td>
</tr>
</table>
</div>
<div class="stepHeading"> Consider Possible Strategies </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="ConsiderPossibleStrategies" name="ConsiderPossibleStrategies"></a>
<div align="left">
    <table border="1" width="100%" cellspacing="0" cellpadding="4" style="border: 1px solid rgb(128,128,128)"     bordercolorlight="#808080" bordercolordark="#808080">
        <tr>
            <td width="5%">
                <b>Purpose:</b>&nbsp;
            </td>
            <td width="95%">
                To identify and outline one or more strategies that will facilitate the required assessment process. &nbsp;
            </td>
        </tr>
    </table><br />
</div>
<p>
    Now that you have a better understanding of the assessment and traceability requirements, and of the constraints placed
    on them by the desired quality level and available process and tool support, you need to consider the potential
    assessment or evaluation strategies you could employ. For a more detailed treatment of possible strategies, we suggest
    you read Cem Kaner's paper "<a href="http://www.kaner.com/pdfs/pnsqc00.pdf" target="_blank"><i>Measurement of the
    Extent of Testing</i></a>," October 2000. (<a href="http://www.adobe.com/products/acrobat/alternate.html">Get Adobe
    Reader</a>)
</p>
<p>
    <b>Sub-topics:</b>
</p>
<ul>
    <li>
        <a href="#TestCoverageStrategy">Test Coverage Analysis</a>
    </li>
    <li>
        <a href="#ResultsStrategy">Test Results Analysis</a>
    </li>
    <li>
        <a href="#DefectStrategy">Defect Analysis</a>
    </li>
</ul>
<h4>
    <a id="TestCoverageStrategy" name="TestCoverageStrategy">Test Coverage Analysis</a> <a href="#ConsiderPossibleStrategies"><img src="./../../rup/resources/top.gif" alt="To top of page" border="0" width="26"     height="20" /></a>
</h4>
<p>
    There are many different approaches to test coverage, and no one coverage measure alone provides all the coverage
    information necessary to form an assessment of the extent or completeness of the test effort. Note that different
    coverage strategies take more or less effort to implement, and with any particular measurement category, there will
    usually be a depth of coverage analysis at which point it becomes uneconomic to record more detailed information.
</p>
<p>
    Some categories of test coverage measurement include: Requirements, Source Code, Product Claims and Standards. We
    recommend you consider incorporating more than one coverage category in your test assessment strategy. In most cases,
    test coverage refers to the planning and implementation of specific tests in the first instance. However, test coverage
    metrics and their analysis are also useful to consider in conjunction with test results or defect analysis.
</p>
<h4>
    <a id="ResultsStrategy" name="ResultsStrategy">Test Results Analysis</a> <a href="#ConsiderPossibleStrategies"><img     src="./../../rup/resources/top.gif" alt="To top of page" border="0" width="26" height="20" /></a>
</h4>
<p>
    A common approach to test results analysis is to simply refer to the number of results that were positive or negative
    as a percentage of the total number of tests run. Our opinion, and the opinion of other practitioner in the test
    community, is that this is a simplistic and incomplete approach to analyzing test results.
</p>
<p>
    Instead, we recommend you analyze your test results in terms of relative trend over time. Within each test cycle,
    consider the relative distribution of test failures across different dimensions such as the functional area being
    tested, the type of quality risks being explored, the relative complexity of the tests and the test resources applied
    to each functional area.
</p>
<h4>
    <a id="DefectStrategy" name="DefectStrategy">Defect Analysis</a> <a href="#ConsiderPossibleStrategies"><img     src="./../../rup/resources/top.gif" alt="To top of page" border="0" width="26" height="20" /></a>
</h4>
<p>
    While defects themselves are obviously related to the results of the test effort, the analysis of defect data does not
    provide any useful information about the progress of the test effort or the completeness or thoroughness of that
    effort. However, a mistake made by some test teams and project managers is to use the current defect count to measure
    the progress of testing or as a gauge to the quality of the developed software. Our opinion, and the opinion of other
    practitioner in the test community, is that this is a meaningless approach.
</p>
<p>
    Instead, we recommend you analyze the relative trend of the defect count over time to provide a measure of relative
    stability. For example, assuming the test effort remains relatively constant, you would typically expect to see the new
    defect discovery rate as measured against a regular time period "bell curve" over the course of the iteration; an
    increasing discovery rate that peaks then tails off toward the end of the iteration. However, you'll need to provide
    this information in conjunction with an analysis of other defect metrics such as: defect resolutions rates, including
    an analysis of the resolution type; distribution of defects by severity; distribution of defects by functional area.
</p>
<p>
    With sophisticated tool support, you can perform complex analysis of defect data relatively easily; without appropriate
    tool support it is a much more difficult proposition.
</p></td>
</tr>
</table>
</div>
<div class="stepHeading"> Discuss Possible Strategies with Stakeholders </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="DiscussPossibleStrategies" name="DiscussPossibleStrategies"></a>
<div align="left">
    <table border="1" width="100%" cellspacing="0" cellpadding="4" style="border: 1px solid rgb(128,128,128)"     bordercolorlight="#808080" bordercolordark="#808080">
        <tr>
            <td width="5%">
                <b>Purpose:</b>&nbsp;
            </td>
            <td width="95%">
                To gather feedback through initial stakeholder review and adjust the strategies as necessary.&nbsp;
            </td>
        </tr>
    </table><br />
</div>
<p>
    Present the possible strategies to the various stakeholders. Typically you'd expect this to include a group made up
    from the following roles; Project Manager, the Software Architect, the Development Manager, the System Analyst, the
    Configuration & Change Manager, the Deployment Manager and the Customer Representative. Each of these roles has a
    stakeholding in how quality is assessed.
</p>
<p>
    Depending on the culture of the project, you should choose an appropriate format to present the possible strategies.
    This might range from one or more informal meetings to a formal presentation or workshop session.
</p></td>
</tr>
</table>
</div>
<div class="stepHeading"> Define and Agree on the Assessment Strategy </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="DefineAgreeAssessmentStrategy" name="DefineAgreeAssessmentStrategy"></a>
<div align="left">
    <table border="1" width="100%" cellspacing="0" cellpadding="4" style="border: 1px solid rgb(128,128,128)"     bordercolorlight="#808080" bordercolordark="#808080">
        <tr>
            <td width="5%">
                <b>Purpose:</b>&nbsp;
            </td>
            <td width="95%">
                To gain stakeholder agreement on the strategy that will be used.&nbsp;
            </td>
        </tr>
    </table><br />
</div>
<p>
    Take the feedback your receive from the discussions and refine the assessment strategy to a single strategy that
    addresses the needs of all stakeholders.
</p>
<p>
    Present the assessment strategy for final agreement and approval.
</p></td>
</tr>
</table>
</div>
<div class="stepHeading"> Define Tool Requirements </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="DefineToolRequirements" name="DefineToolRequirements"></a>
<div align="left">
    <table border="1" width="100%" cellspacing="0" cellpadding="4" style="border: 1px solid rgb(128,128,128)"     bordercolorlight="#808080" bordercolordark="#808080">
        <tr>
            <td width="5%">
                <b>Purpose:</b>&nbsp;
            </td>
            <td width="95%">
                To define the supporting tool configuration requirements that will enable the assessment process.&nbsp;
            </td>
        </tr>
    </table><br />
</div>
<p>
    As mentioned previously, with sophisticated tool support you can perform complex analysis of measurement data
    relatively easily; without appropriate tool support it is a much more difficult proposition.
</p>
<p>
    For the following categories, consider what tool support you will need: Coverage and Traceability, Defect Analysis.
</p></td>
</tr>
</table>
</div>
<div class="stepHeading"> Evaluate and Verify Your Results </div>
<div class="stepContent">
<table class="stepTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td><a id="EvaluateResults" name="EvaluateResults"></a>
<div align="left">
    <table border="1" width="100%" cellspacing="0" cellpadding="4" style="border: 1px solid rgb(128,128,128)"     bordercolorlight="#808080" bordercolordark="#808080">
        <tr>
            <td width="5%">
                <b>Purpose:</b>&nbsp;
            </td>
            <td width="95%">
                To verify that the task has been completed appropriately and that the resulting work products are
                acceptable.&nbsp;
            </td>
        </tr>
    </table><br />
</div>
<p>
    Now that you have completed the work, it is beneficial to verify that the work was of sufficient value, and that you
    did not simply consume vast quantities of paper. You should evaluate whether your work is of appropriate quality, and
    that it is complete enough to be useful to those team members who will make subsequent use of it as input to their
    work. Where possible, use the checklists provided in NUP to verify that quality and completeness are "good enough."
</p>
<p>
    Have the people performing the downstream tasks that rely on your work as input take part in reviewing your interim
    work. Do this while you still have time available to take action to address their concerns. You should also evaluate
    your work against the key input work products to make sure you have represented them accurately and sufficiently. It
    might be useful to have the author of the input work product review your work on this basis.
</p>
<p>
    Try to remember that that NUP is an iterative process and that in many cases work products evolve over time. As such,
    it is not usually necessary-and is often counterproductive-to fully-form a work product that will only be partially
    used or will not be used at all in immediately subsequent work. This is because there is a high probability that the
    situation surrounding the work product will change-and the assumptions made when the work product was created proven
    incorrect-before the work product is used, resulting in wasted effort and costly rework. Also avoid the trap of
    spending too many cycles on presentation to the detriment of content value. In project environments where presentation
    has importance and economic value as a project deliverable, you might want to consider using an administrative resource
    to perform presentation tasks.
</p><br />
<br /></td>
</tr>
</table>
</div>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Properties</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Multiple Occurrences" abbr="Multiple Occurrences">Multiple Occurrences</th><td class="sectionTableCell" align="left" headers="property_Multiple Occurrences"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Event Driven" abbr="Event Driven">Event Driven</th><td class="sectionTableCell" align="left" headers="property_Event Driven"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Ongoing" abbr="Ongoing">Ongoing</th><td class="sectionTableCell" align="left" headers="property_Ongoing"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Optional" abbr="Optional">Optional</th><td class="sectionTableCell" align="left" headers="property_Optional"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Planned" abbr="Planned">Planned</th><td class="sectionTableCell" align="left" headers="property_Planned"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
<tr valign="top">
<th class="sectionTableHeading" scope="row" id="property_Repeatable" abbr="Repeatable">Repeatable</th><td class="sectionTableCell" align="left" headers="property_Repeatable"><img width="20" height="15" alt="" title="" src="./../../images/indent.gif"></td>
</tr>
</table>
</div>
<table class="copyright" border="0" cellspacing="0" cellpadding="0">
<tr>
<td class="copyright">Copyright &copy; 2008 版权所有 东软集团股份有限公司&nbsp; 联系邮箱:<a href="mailto:tcoe@neusoft.com">tcoe@neusoft.com</a></td>
</tr>
</table>
</td>
</tr>
</table>
</body>
<script language="JavaScript" type="text/javascript">
					contentPage.onload();
					contentPage.processPage.fixDescriptorLinks();
				</script>
</html>
